-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Normalize directly in the same String instance #582
Conversation
BenchmarksComparisonBenchmark execution time: 2024-08-08 06:35:31 Comparing candidate commit a023ff8 in PR branch Found 15 performance improvements and 0 performance regressions! Performance is the same for 35 metrics, 2 unstable metrics. scenario:normalization/normalize_name/normalize_name/bad-name
scenario:normalization/normalize_name/normalize_name/good
scenario:normalization/normalize_service/normalize_service/A0000000000000000000000000000000000000000000000000...
scenario:normalization/normalize_service/normalize_service/Data🐨dog🐶 繋がっ⛰てて
scenario:normalization/normalize_service/normalize_service/Test Conversion 0f Weird !@#$%^&**() Characters
scenario:normalization/normalize_service/normalize_service/[empty string]
scenario:normalization/normalize_service/normalize_service/test_ASCII
scenario:normalization/normalize_trace/test_trace
CandidateCandidate benchmark detailsGroup 1
Group 2
Group 3
Group 4
Group 5
Group 6
Group 7
Group 8
Group 9
Group 10
Group 11
BaselineOmitted due to size. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #582 +/- ##
==========================================
- Coverage 71.30% 71.26% -0.04%
==========================================
Files 220 220
Lines 29904 29924 +20
==========================================
+ Hits 21322 21326 +4
- Misses 8582 8598 +16
|
63cd1ac
to
a023ff8
Compare
What does this PR do?
This changes the in place normalization to directly manipulate the underlying
Vec
instance.Motivation
While working on stabilizing the benchmark results I looked at what allocated things on the heap, and came across this small change.
Additional Notes
Nope.
How to test the change?
The benchmarks and tests should cover it.